Release 10.1A: OpenEdge Development:
Progress Dynamics Repository Reference

gsc_service_type table — gscst

This table describes the different types of services available to applications and provides the management procedures for the different types of connections. Database services, AppServer services, Web Services, and JMS partitions are examples of different service types. The Database, Web Services, and AppServer services are system-owned.

Table 13–7 lists the table’s FLA, fields, and foreign keys.

Table 13–7: gsc_service_type table information 

Table FLA	Fields (data type)	Foreign keys
gscst	service_type_obj (Decimal) service_type_code (Character) service_type_description (Character) management_object_obj (Decimal) maintenance_object_obj (Decimal) default_logical_service_obj (Decimal)	service_type_obj

Table 13–8 gives details of the table’s indexes.

Table 13–8: gsc_service_type index information 

Index name	Elements	Type
XPKgsc_service_type	service_type_obj	Primary Unique
XAK1gsc_service_type	service_type_code	Unique
XIE1gsc_service_type	service_type_description	Nonunique
XIE4gsc_service_type	default_logical_service_obj	Nonunique
XIE5gsc_service_type	maintenance_object_obj	Nonunique
XIE6gsc_service_type	management_object_obj	Nonunique

The maintenance object defines the datafield object used to maintain the physical connection parameter attribute on the physical service table. For example, if this is a database connection service type, then the datafield can allow the specification of -S, -N, and -H prompts independently. It can then put the result as a single field into the connection parameter.

In the case of Web services, there are many connection parameters, some of which are only known at run time. To support this, the gsm_physical_service table supports substitution lists. The substitution list contains token value lists delimited by CHR(1), the token and value are delimited by CHR(3).

The tokens are %<parameter_name> or a special token, %DynUserID, that is replaced by the Progress Dynamics user id of the current user. For example, tokens can be defined for parameters as follows:

WSDL UserId = %WSDLUserId WSDL Password = %WSDLPassword SOAPEndpoint UserId = %DynUserID SOAPEndpoint Password = %SOAPEndpointPassword MaxConnections = %maxConnections

The management object is the API procedure that is responsible for making the physical connections to the service. In the case of an AppServer partition, the default logical service could point at the default logical AppServer partition to use.